home *** CD-ROM | disk | FTP | other *** search
- /* port.h header for KISS */
- #include <exec/ports.h>
-
- /*
- Worst case length of a message is when writing a message composed
- entirely of escape characters
- */
- #define MAXLEN 550
- struct kiss_msg {
- struct Message cm; /* This must be first */
- short channel; /* When sent to reader this is a command */
- short msgsize; /* Number of data bytes in msg[] */
- char rport;
- char rstream;
- char junk[4]; /* Eight bytes precede the actual message */
- char fend;
- char cmd; /* and can be used for any purpose */
- char port; /* KAM host mode uses the last 4 for the */
- char stream; /* fend, command, port and stream bytes */
- unsigned char msg[MAXLEN];
- };
-
- struct regd {
- struct kiss_msg mp; /* This must be first */
- struct regd *fwd;
- };
-
-
- /* Port names. In wa8ded only the ctl-name is used. */
- #define CTL_NAME "VE5VA-HOST"
- #define WRT_NAME "VE5VA-WRITE"
-
- /* Commands for processes registering or otherwise communicating with
- the control process
- */
- #define K_MONITOR 1
- #define K_REGISTER 2
- #define K_SHUTUP 3
- #define K_WRT_DATA 4 /* Normal data - needs escape processing */
- #define K_WRT_CMND 5
- #define K_BEEP 6
- #define K_SHUTDOWN 7
- #define K_WRT_RAW 8 /* Guaranteed that escape processing not needed */
- #define K_GET_STAT 9
-
-
- #define B_GET_STAT 1
-
-
-
- /* The original CBBS code is written such that if a process does a
- lock, that lock applies to all of them. But that is not really
- necessary. It could have different locks, one for each code segment
- so that if one piece of code locks out the others from writing into
- the mail file, there's no reason why another process could not be
- writing in the BID file using a different lock. If I have time I'll
- implement different locks for each one.
- Better yet, remove all file operations from the BBS altogether and
- make them separate processes which control who does what when.
- */
-